Software Engineering

M. Latha ¹, K. Duraiswamy ²

Affiliations
1 Department of Computer Science, Sri Sarada College for Women, Salem-16, IN
2 K.S.R. College of Engineering, K.S.R. Kalvi Nagar, Tiruchengode, IN

Abstract

The Object-Oriented paradigm has become increasingly popular in recent years. Researchers agree that, although maintenance may turn out to be easier for Object-Oriented systems, it is unlikely that the maintenance burden will completely disappear.One approach to controlling software maintenance costs is the utilization of software metrics during the development phase, to help identify potential problem areas. Many new metrics have been proposed for Object-Oriented systems.

The purpose of this work is to apply three existing Object-Oriented design complexity metrics and, specifically, to assess their ability to predict maintenance time for the polymorphism process.This research reports the results of validating three metrics,Interaction Level (IL), Interface Size (IS), and Operation Argument Complexity (OAC).

This system is designed to estimate maintenance time for the software's that are developed by using java. A controlled experiment was conducted to investigate the effect of design complexity (as measured by the above metrics) on maintenance time. Each of the three metrics by itself was found to be useful in the experiment in predicting maintenance performance.

Keywords

Interface Size Interaction Level Maintenance Time, Operation Argument Complexity.

Full Text

     

M. Latha ¹, K. Duraiswamy ²

Affiliations
1 Department of Computer Science, Sri Sarada College for Women, Salem-16, IN
2 K.S.R College of Engineering, K.S.R Kalvi Nagar, Tiruchengode, IN

Abstract

The Object-Oriented paradigm has become increasingly popular in recent years. Researchers agree that, although maintenance may turn out to be easier for Object-Oriented systems, it is unlikely that the maintenance burden will completely disappear. One approach to controlling software maintenance costs is the utilization of software metrics during the development phase, to help identify potential problem areas. Many new metrics have been proposed for Object-Oriented systems.

The purpose of this work is to apply three existing Object-Oriented design complexity metrics and, specifically, to assess their ability to predict maintenance time for the inheritance process. This research reports the results of validating three metrics, Interaction Level (IL), Interface Size (IS), and Operation Argument Complexity (OAC).

This system is designed to estimate maintenance time for the software's that are developed by using java. A controlled experiment was conducted to investigate the effect of design complexity (as measured by the above metrics) on maintenance time. Each of the three metrics by itself was found to be useful in the experiment in predicting maintenance performance.

Keywords

Interface Size Interaction Level Maintenance Time, Operation Argument Complexity.

Full Text

     

P. M. Shanthi ¹, K. Duraiswamy ²

Affiliations
1 Department of MCA, K.S.Rangasamy College of Technology, Tiruchengode-637 215, IN
2 Department of Computer Science and Engineering, K.S.Rangasamy College of Technology, Tiruchengode-637 215, IN

Abstract

In this computerized world, software growth rate is increasing steadily. Some company‘s plays an important role in this growth by developing and releasing new software to lead a leading position in the software development process. In order to make the product to be used by most of the people, the company releases their product as free software. The free software is a open source software which can be downloaded and utilized by all kinds of user with free of cost. (i.e,) No cost for downloading the software. The open source software is the software that is developed without proper management. The quality and reliability of this software is not well designed. Since this software is an open source, the user is the only responsible person to solve all their problems faced in that software. The problem may arise while utilizing this software. Some of the problems faced by the user are they may not be aware of its purpose, performance, usefulness or there may occur some errors. Due to these problems, the user may get confused of whether use this software further or leave it and search for an alternate one. They may also search for an alternate if they not understand the errors occurred in this software. In such situation, the rate of people accessing this software becomes low. In order to help the users to manage the problems, we propose a fault tolerant technique in this paper. In this technique, the errors found in the open source software is automatically detected and reported. The fault tolerant is the technology that will tolerate the fault found in the software automatically and so the technology is termed as Automated Software. In this paper, we propose this fault tolerant technology in the open source software, to find the error rate automatically. Due to this automated technique, the rate of the people utilizing the software becomes more. The aim of the paper is to propose a strategy to determine the performance of the open source software by deducing the error found in that software. This aim has to be achieved by deriving an algorithm to open and read the software and also to determine the errors automatically. Thus this paper implements an effective methodology in order to make the open source software useful by means of an automated fault tolerant technique to deduct and report the error found in the software, and to decrease the problem rate and manual effort.

Keywords

Automated Software, Computerized world, Deduce Error, Download, Effective Methodology, Error Rate, Error Report, Fault Tolerant, Free Software, Open Source Software.

Full Text

     

M. Latha ¹, K. Duraiswamy ²

Affiliations
1 Sri College for Women, IN
2 K.S.R. College of Engineering & Tech, IN

Abstract

The Object-Oriented paradigm has become increasingly popular in recent years. Researchers agree that, although maintenance may turn out to be easier for Object-Oriented systems, it is unlikely that the maintenance burden will completely disappear. One approach to controlling software maintenance costs is the utilization of software metrics during the development phase, to help identify potential problem areas. Many new metrics have been proposed for Object-Oriented systems. The purpose of this work is to apply three existing Object-Oriented design complexity metrics and, specifically, to assess their ability to predict maintenance time for the reverse engineering process. This research reports the results of validating three metrics, Interaction Level (IL), Interface Size (IS), and Operation Argument Complexity (OAC). This system is designed to estimate maintenance time for the softwares that are developed by using java. A controlled experiment was conducted to investigate the effect of design complexity (as measured by the above metrics) on maintenance time. Each of the three metrics by itself was found to be useful in the experiment in predicting maintenance performance.

Keywords

Interaction Level, Interface Size, Maintenance Time, Operation Argument Complexity.

Full Text